3.x: Handle empty metadataid when metadataid feature is on #757
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dkropachev
approved these changes
Nov 6, 2025
|
Looks like majority of tests are failed due to the bug in testing framework |
|
Something is off, i rerun pipeline on |
nikagra
changed the title
resultMetadataId in Execute message
nikagra
force-pushed
the
3.x_empty_resultMetadataId_fix
branch
2 times, most recently
from
b019cbc to
0f3ae37
Compare
nikagra
force-pushed
the
3.x_empty_resultMetadataId_fix
branch
from
0f3ae37 to
163c6ac
Compare
dkropachev
approved these changes
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addressing #755, which is a corner case of work done as part of #597.
Changes:
nullvalue ofresultMetadataId, using empty byte array instead inExectutemessage.